-- Network Working Group D. Levi
-- Request for Comments: 3413 Nortel Networks
-- STD: 62 P. Meyer
-- Obsoletes: 2573 Secure Computing Corporation
-- Category: Standards Track B. Stewart
-- Retired
-- December 2002-- Simple Network Management Protocol (SNMP) ApplicationsSNMP-TARGET-MIB DEFINITIONS::=BEGINIMPORTSMODULE-IDENTITY,OBJECT-TYPE,snmpModules,
Counter32,Integer32FROM SNMPv2-SMI
TEXTUAL-CONVENTION,TDomain,TAddress,TimeInterval,RowStatus,StorageType,TestAndIncrFROM SNMPv2-TC
SnmpSecurityModel,SnmpMessageProcessingModel,SnmpSecurityLevel,SnmpAdminStringFROM SNMP-FRAMEWORK-MIB
MODULE-COMPLIANCE,OBJECT-GROUPFROM SNMPv2-CONF;snmpTargetMIB MODULE-IDENTITYLAST-UPDATED"200210140000Z"
ORGANIZATION"IETF SNMPv3 Working Group"CONTACT-INFO"WG-email: snmpv3@lists.tislabs.com
Subscribe: majordomo@lists.tislabs.com
In message body: subscribe snmpv3
Co-Chair: Russ Mundy
Network Associates Laboratories
Postal: 15204 Omega Drive, Suite 300
Rockville, MD 20850-4601
USA
EMail: mundy@tislabs.com
Phone: +1 301-947-7107
Co-Chair: David Harrington
Enterasys Networks
Postal: 35 Industrial Way
P. O. Box 5004
Rochester, New Hampshire 03866-5005
USA
EMail: dbh@enterasys.com
Phone: +1 603-337-2614
Co-editor: David B. Levi
Nortel Networks
Postal: 3505 Kesterwood Drive
Knoxville, Tennessee 37918
EMail: dlevi@nortelnetworks.com
Phone: +1 865 686 0432
Co-editor: Paul Meyer
Secure Computing Corporation
Postal: 2675 Long Lake Road
Roseville, Minnesota 55113
EMail: paul_meyer@securecomputing.com
Phone: +1 651 628 1592
Co-editor: Bob Stewart
Retired"DESCRIPTION"This MIB module defines MIB objects which provide
mechanisms to remotely configure the parameters used
by an SNMP entity for the generation of SNMP messages.
Copyright (C) The Internet Society (2002). This
version of this MIB module is part of RFC 3413;
see the RFC itself for full legal notices.
"REVISION"200210140000Z"-- 14 October 2002DESCRIPTION"Fixed DISPLAY-HINTS for UTF-8 strings, fixed hex
value of LF characters, clarified meaning of zero
length tag values, improved tag list examples.
Published as RFC 3413."REVISION"199808040000Z"-- 4 August 1998
DESCRIPTION"Clarifications, published as
RFC 2573."REVISION"199707140000Z"-- 14 July 1997DESCRIPTION"The initial revision, published as RFC2273."::={ snmpModules 12}snmpTargetObjects OBJECTIDENTIFIER::={ snmpTargetMIB 1}snmpTargetConformance OBJECTIDENTIFIER::={ snmpTargetMIB 3}SnmpTagValue::=TEXTUAL-CONVENTIONDISPLAY-HINT"255t"STATUScurrent
DESCRIPTION"An octet string containing a tag value.
Tag values are preferably in human-readable form.
To facilitate internationalization, this information
is represented using the ISO/IEC IS 10646-1 character
set, encoded as an octet string using the UTF-8
character encoding scheme described in RFC 2279.
Since additional code points are added by amendments
to the 10646 standard from time to time,
implementations must be prepared to encounter any code
point from 0x00000000 to 0x7fffffff.
The use of control codes should be avoided, and certain
control codes are not allowed as described below.
For code points not directly supported by user
interface hardware or software, an alternative means
of entry and display, such as hexadecimal, may be
provided.
For information encoded in 7-bit US-ASCII, the UTF-8
representation is identical to the US-ASCII encoding.
Note that when this TC is used for an object that
is used or envisioned to be used as an index, then a
SIZE restriction must be specified so that the number
of sub-identifiers for any object instance does not
exceed the limit of 128, as defined by [RFC1905].
An object of this type contains a single tag value
which is used to select a set of entries in a table.
A tag value is an arbitrary string of octets, but
may not contain a delimiter character. Delimiter
characters are defined to be one of the following:
- An ASCII space character (0x20).
- An ASCII TAB character (0x09).
- An ASCII carriage return (CR) character (0x0D).
- An ASCII line feed (LF) character (0x0A).
Delimiter characters are used to separate tag values
in a tag list. An object of this type may only
contain a single tag value, and so delimiter
characters are not allowed in a value of this type.
Note that a tag value of 0 length means that no tag is
defined. In other words, a tag value of 0 length would
never match anything in a tag list, and would never
select any table entries.
Some examples of valid tag values are:
- 'acme'
- 'router'
- 'host'
The use of a tag value to select table entries is
application and MIB specific."SYNTAXOCTETSTRING(SIZE(0..255))SnmpTagList::=TEXTUAL-CONVENTIONDISPLAY-HINT"255t"STATUScurrentDESCRIPTION"An octet string containing a list of tag values.
Tag values are preferably in human-readable form.
To facilitate internationalization, this information
is represented using the ISO/IEC IS 10646-1 character
set, encoded as an octet string using the UTF-8
character encoding scheme described in RFC 2279.
Since additional code points are added by amendments
to the 10646 standard from time to time,
implementations must be prepared to encounter any code
point from 0x00000000 to 0x7fffffff.
The use of control codes should be avoided, except as
described below.
For code points not directly supported by user
interface hardware or software, an alternative means
of entry and display, such as hexadecimal, may be
provided.
For information encoded in 7-bit US-ASCII, the UTF-8
representation is identical to the US-ASCII encoding.
An object of this type contains a list of tag values
which are used to select a set of entries in a table.
A tag value is an arbitrary string of octets, but
may not contain a delimiter character. Delimiter
characters are defined to be one of the following:
- An ASCII space character (0x20).
- An ASCII TAB character (0x09).
- An ASCII carriage return (CR) character (0x0D).
- An ASCII line feed (LF) character (0x0A).
Delimiter characters are used to separate tag values
in a tag list. Only a single delimiter character may
occur between two tag values. A tag value may not
have a zero length. These constraints imply certain
restrictions on the contents of this object:
- There cannot be a leading or trailing delimiter
character.
- There cannot be multiple adjacent delimiter
characters.
Some examples of valid tag lists are:
- '' -- an empty list
- 'acme' -- list of one tag
- 'host router bridge' -- list of several tags
Note that although a tag value may not have a length of
zero, an empty string is still valid. This indicates
an empty list (i.e. there are no tag values in the list).
The use of the tag list to select table entries is
application and MIB specific. Typically, an application
will provide one or more tag values, and any entry
which contains some combination of these tag values
will be selected."SYNTAXOCTETSTRING(SIZE(0..255))
------ The snmpTargetObjects group----snmpTargetSpinLock OBJECT-TYPESYNTAXTestAndIncrMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This object is used to facilitate modification of table
entries in the SNMP-TARGET-MIB module by multiple
managers. In particular, it is useful when modifying
the value of the snmpTargetAddrTagList object.
The procedure for modifying the snmpTargetAddrTagList
object is as follows:
1. Retrieve the value of snmpTargetSpinLock and
of snmpTargetAddrTagList.
2. Generate a new value for snmpTargetAddrTagList.
3. Set the value of snmpTargetSpinLock to the
retrieved value, and the value of
snmpTargetAddrTagList to the new value. If
the set fails for the snmpTargetSpinLock
object, go back to step 1."::={ snmpTargetObjects 1}snmpTargetAddrTable OBJECT-TYPESYNTAXSEQUENCEOF SnmpTargetAddrEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A table of transport addresses to be used in the generation
of SNMP messages."::={ snmpTargetObjects 2}snmpTargetAddrEntry OBJECT-TYPESYNTAX SnmpTargetAddrEntry
MAX-ACCESSnot-accessibleSTATUScurrent
DESCRIPTION"A transport address to be used in the generation
of SNMP operations.
Entries in the snmpTargetAddrTable are created and
deleted using the snmpTargetAddrRowStatus object."INDEX{IMPLIED snmpTargetAddrName }::={ snmpTargetAddrTable 1}
SnmpTargetAddrEntry ::=SEQUENCE{
snmpTargetAddrName SnmpAdminString,
snmpTargetAddrTDomain TDomain,
snmpTargetAddrTAddress TAddress,
snmpTargetAddrTimeout TimeInterval,
snmpTargetAddrRetryCount Integer32,
snmpTargetAddrTagList SnmpTagList,
snmpTargetAddrParams SnmpAdminString,
snmpTargetAddrStorageType StorageType,
snmpTargetAddrRowStatus RowStatus}snmpTargetAddrName OBJECT-TYPESYNTAXSnmpAdminString(SIZE(1..32))MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The locally arbitrary, but unique identifier associated
with this snmpTargetAddrEntry."::={ snmpTargetAddrEntry 1}snmpTargetAddrTDomain OBJECT-TYPESYNTAXTDomainMAX-ACCESSread-createSTATUScurrent
DESCRIPTION"This object indicates the transport type of the address
contained in the snmpTargetAddrTAddress object."::={ snmpTargetAddrEntry 2}snmpTargetAddrTAddress OBJECT-TYPESYNTAXTAddressMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object contains a transport address. The format of
this address depends on the value of the
snmpTargetAddrTDomain object."::={ snmpTargetAddrEntry 3}snmpTargetAddrTimeout OBJECT-TYPESYNTAXTimeIntervalMAX-ACCESSread-create
STATUScurrentDESCRIPTION"This object should reflect the expected maximum round
trip time for communicating with the transport address
defined by this row. When a message is sent to this
address, and a response (if one is expected) is not
received within this time period, an implementation
may assume that the response will not be delivered.
Note that the time interval that an application waits
for a response may actually be derived from the value
of this object. The method for deriving the actual time
interval is implementation dependent. One such method
is to derive the expected round trip time based on a
particular retransmission algorithm and on the number
of timeouts which have occurred. The type of message may
also be considered when deriving expected round trip
times for retransmissions. For example, if a message is
being sent with a securityLevel that indicates both
authentication and privacy, the derived value may be
increased to compensate for extra processing time spent
during authentication and encryption processing."DEFVAL{1500}::={ snmpTargetAddrEntry 4}snmpTargetAddrRetryCount OBJECT-TYPESYNTAXInteger32(0..255)MAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object specifies a default number of retries to be
attempted when a response is not received for a generated
message. An application may provide its own retry count,
in which case the value of this object is ignored."DEFVAL{3}::={ snmpTargetAddrEntry 5}
snmpTargetAddrTagList OBJECT-TYPESYNTAXSnmpTagListMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object contains a list of tag values which are
used to select target addresses for a particular
operation."DEFVAL{""}::={ snmpTargetAddrEntry 6}snmpTargetAddrParams OBJECT-TYPESYNTAXSnmpAdminString(SIZE(1..32))MAX-ACCESSread-create
STATUScurrentDESCRIPTION"The value of this object identifies an entry in the
snmpTargetParamsTable. The identified entry
contains SNMP parameters to be used when generating
messages to be sent to this transport address."::={ snmpTargetAddrEntry 7}snmpTargetAddrStorageType OBJECT-TYPESYNTAXStorageTypeMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The storage type for this conceptual row.
Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row."DEFVAL{ nonVolatile }::={ snmpTargetAddrEntry 8}
snmpTargetAddrRowStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The status of this conceptual row.
To create a row in this table, a manager must
set this object to either createAndGo(4) or
createAndWait(5).
Until instances of all corresponding columns are
appropriately configured, the value of the
corresponding instance of the snmpTargetAddrRowStatus
column is 'notReady'.
In particular, a newly created row cannot be made
active until the corresponding instances of
snmpTargetAddrTDomain, snmpTargetAddrTAddress, and
snmpTargetAddrParams have all been set.
The following objects may not be modified while the
value of this object is active(1):
- snmpTargetAddrTDomain
- snmpTargetAddrTAddress
An attempt to set these objects while the value of
snmpTargetAddrRowStatus is active(1) will result in
an inconsistentValue error."::={ snmpTargetAddrEntry 9}snmpTargetParamsTable OBJECT-TYPESYNTAXSEQUENCEOF SnmpTargetParamsEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"A table of SNMP target information to be used
in the generation of SNMP messages."::={ snmpTargetObjects 3}snmpTargetParamsEntry OBJECT-TYPESYNTAX SnmpTargetParamsEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION
"A set of SNMP target information.
Entries in the snmpTargetParamsTable are created and
deleted using the snmpTargetParamsRowStatus object."INDEX{IMPLIED snmpTargetParamsName }::={ snmpTargetParamsTable 1}
SnmpTargetParamsEntry ::=SEQUENCE{
snmpTargetParamsName SnmpAdminString,
snmpTargetParamsMPModel SnmpMessageProcessingModel,
snmpTargetParamsSecurityModel SnmpSecurityModel,
snmpTargetParamsSecurityName SnmpAdminString,
snmpTargetParamsSecurityLevel SnmpSecurityLevel,
snmpTargetParamsStorageType StorageType,
snmpTargetParamsRowStatus RowStatus
}snmpTargetParamsName OBJECT-TYPESYNTAXSnmpAdminString(SIZE(1..32))MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The locally arbitrary, but unique identifier associated
with this snmpTargetParamsEntry."::={ snmpTargetParamsEntry 1}snmpTargetParamsMPModel OBJECT-TYPESYNTAXSnmpMessageProcessingModelMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The Message Processing Model to be used when generating
SNMP messages using this entry."::={ snmpTargetParamsEntry 2}snmpTargetParamsSecurityModel OBJECT-TYPESYNTAXSnmpSecurityModel(1..2147483647)MAX-ACCESSread-createSTATUScurrentDESCRIPTION"The Security Model to be used when generating SNMP
messages using this entry. An implementation may
choose to return an inconsistentValue error if an
attempt is made to set this variable to a value
for a security model which the implementation does
not support."::={ snmpTargetParamsEntry 3}snmpTargetParamsSecurityName OBJECT-TYPE
SYNTAXSnmpAdminStringMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The securityName which identifies the Principal on
whose behalf SNMP messages will be generated using
this entry."::={ snmpTargetParamsEntry 4}snmpTargetParamsSecurityLevel OBJECT-TYPESYNTAXSnmpSecurityLevelMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The Level of Security to be used when generating
SNMP messages using this entry."::={ snmpTargetParamsEntry 5}snmpTargetParamsStorageType OBJECT-TYPE
SYNTAXStorageTypeMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The storage type for this conceptual row.
Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row."DEFVAL{ nonVolatile }::={ snmpTargetParamsEntry 6}snmpTargetParamsRowStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The status of this conceptual row.
To create a row in this table, a manager must
set this object to either createAndGo(4) or
createAndWait(5).
Until instances of all corresponding columns are
appropriately configured, the value of the
corresponding instance of the snmpTargetParamsRowStatus
column is 'notReady'.
In particular, a newly created row cannot be made
active until the corresponding
snmpTargetParamsMPModel,
snmpTargetParamsSecurityModel,
snmpTargetParamsSecurityName,
and snmpTargetParamsSecurityLevel have all been set.
The following objects may not be modified while the
value of this object is active(1):
- snmpTargetParamsMPModel
- snmpTargetParamsSecurityModel
- snmpTargetParamsSecurityName
- snmpTargetParamsSecurityLevel
An attempt to set these objects while the value of
snmpTargetParamsRowStatus is active(1) will result in
an inconsistentValue error."::={ snmpTargetParamsEntry 7}snmpUnavailableContexts OBJECT-TYPESYNTAXCounter32
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of packets received by the SNMP
engine which were dropped because the context
contained in the message was unavailable."::={ snmpTargetObjects 4}snmpUnknownContexts OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of packets received by the SNMP
engine which were dropped because the context
contained in the message was unknown."::={ snmpTargetObjects 5}----
-- Conformance information----snmpTargetCompliances OBJECTIDENTIFIER::={ snmpTargetConformance 1}snmpTargetGroups OBJECTIDENTIFIER::={ snmpTargetConformance 2}------ Compliance statements----snmpTargetCommandResponderCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for SNMP entities which include
a command responder application."MODULE-- This Module
MANDATORY-GROUPS{ snmpTargetCommandResponderGroup }::={ snmpTargetCompliances 1}snmpTargetBasicGroup OBJECT-GROUPOBJECTS{
snmpTargetSpinLock,
snmpTargetAddrTDomain,
snmpTargetAddrTAddress,
snmpTargetAddrTagList,
snmpTargetAddrParams,
snmpTargetAddrStorageType,
snmpTargetAddrRowStatus,
snmpTargetParamsMPModel,
snmpTargetParamsSecurityModel,
snmpTargetParamsSecurityName,
snmpTargetParamsSecurityLevel,
snmpTargetParamsStorageType,
snmpTargetParamsRowStatus
}STATUScurrent
DESCRIPTION"A collection of objects providing basic remote
configuration of management targets."::={ snmpTargetGroups 1}snmpTargetResponseGroup OBJECT-GROUPOBJECTS{
snmpTargetAddrTimeout,
snmpTargetAddrRetryCount
}STATUScurrentDESCRIPTION"A collection of objects providing remote configuration
of management targets for applications which generate
SNMP messages for which a response message would be
expected."::={ snmpTargetGroups 2}snmpTargetCommandResponderGroup OBJECT-GROUPOBJECTS{
snmpUnavailableContexts,
snmpUnknownContexts
}STATUScurrentDESCRIPTION"A collection of objects required for command responder
applications, used for counting error conditions."::={ snmpTargetGroups 3}ENDSNMP-NOTIFICATION-MIB DEFINITIONS::=BEGINIMPORTSMODULE-IDENTITY,OBJECT-TYPE,snmpModules
FROM SNMPv2-SMI
RowStatus,StorageTypeFROM SNMPv2-TC
SnmpAdminStringFROM SNMP-FRAMEWORK-MIB
SnmpTagValue,snmpTargetParamsName
FROM SNMP-TARGET-MIB
MODULE-COMPLIANCE,OBJECT-GROUPFROM SNMPv2-CONF;snmpNotificationMIB MODULE-IDENTITYLAST-UPDATED"200210140000Z"ORGANIZATION"IETF SNMPv3 Working Group"CONTACT-INFO"WG-email: snmpv3@lists.tislabs.com
Subscribe: majordomo@lists.tislabs.com
In message body: subscribe snmpv3
Co-Chair: Russ Mundy
Network Associates Laboratories
Postal: 15204 Omega Drive, Suite 300
Rockville, MD 20850-4601
USA
EMail: mundy@tislabs.com
Phone: +1 301-947-7107
Co-Chair: David Harrington
Enterasys Networks
Postal: 35 Industrial Way
P. O. Box 5004
Rochester, New Hampshire 03866-5005
USA
EMail: dbh@enterasys.com
Phone: +1 603-337-2614
Co-editor: David B. Levi
Nortel Networks
Postal: 3505 Kesterwood Drive
Knoxville, Tennessee 37918
EMail: dlevi@nortelnetworks.com
Phone: +1 865 686 0432
Co-editor: Paul Meyer
Secure Computing Corporation
Postal: 2675 Long Lake Road
Roseville, Minnesota 55113
EMail: paul_meyer@securecomputing.com
Phone: +1 651 628 1592
Co-editor: Bob Stewart
Retired"DESCRIPTION"This MIB module defines MIB objects which provide
mechanisms to remotely configure the parameters
used by an SNMP entity for the generation of
notifications.
Copyright (C) The Internet Society (2002). This
version of this MIB module is part of RFC 3413;
see the RFC itself for full legal notices.
"REVISION"200210140000Z"-- 14 October 2002
DESCRIPTION"Clarifications, published as
RFC 3413."REVISION"199808040000Z"-- 4 August 1998DESCRIPTION"Clarifications, published as
RFC 2573."REVISION"199707140000Z"-- 14 July 1997DESCRIPTION"The initial revision, published as RFC2273."::={ snmpModules 13}snmpNotifyObjects OBJECTIDENTIFIER::={ snmpNotificationMIB 1}snmpNotifyConformance OBJECTIDENTIFIER::={ snmpNotificationMIB 3}
------ The snmpNotifyObjects group----snmpNotifyTable OBJECT-TYPESYNTAXSEQUENCEOF SnmpNotifyEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table is used to select management targets which should
receive notifications, as well as the type of notification
which should be sent to each selected management target."::={ snmpNotifyObjects 1}snmpNotifyEntry OBJECT-TYPESYNTAX SnmpNotifyEntry
MAX-ACCESSnot-accessibleSTATUScurrent
DESCRIPTION"An entry in this table selects a set of management targets
which should receive notifications, as well as the type of
notification which should be sent to each selected
management target.
Entries in the snmpNotifyTable are created and
deleted using the snmpNotifyRowStatus object."INDEX{IMPLIED snmpNotifyName }::={ snmpNotifyTable 1}
SnmpNotifyEntry ::=SEQUENCE{
snmpNotifyName SnmpAdminString,
snmpNotifyTag SnmpTagValue,
snmpNotifyType INTEGER,
snmpNotifyStorageType StorageType,
snmpNotifyRowStatus RowStatus
}snmpNotifyName OBJECT-TYPESYNTAXSnmpAdminString(SIZE(1..32))MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The locally arbitrary, but unique identifier associated
with this snmpNotifyEntry."::={ snmpNotifyEntry 1}snmpNotifyTag OBJECT-TYPESYNTAXSnmpTagValueMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object contains a single tag value which is used
to select entries in the snmpTargetAddrTable. Any entry
in the snmpTargetAddrTable which contains a tag value
which is equal to the value of an instance of this
object is selected. If this object contains a value
of zero length, no entries are selected."DEFVAL{""}::={ snmpNotifyEntry 2}snmpNotifyType OBJECT-TYPESYNTAXINTEGER{trap(1),inform(2)}MAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object determines the type of notification to
be generated for entries in the snmpTargetAddrTable
selected by the corresponding instance of
snmpNotifyTag. This value is only used when
generating notifications, and is ignored when
using the snmpTargetAddrTable for other purposes.
If the value of this object is trap(1), then any
messages generated for selected rows will contain
Unconfirmed-Class PDUs.
If the value of this object is inform(2), then any
messages generated for selected rows will contain
Confirmed-Class PDUs.
Note that if an SNMP entity only supports
generation of Unconfirmed-Class PDUs (and not
Confirmed-Class PDUs), then this object may be
read-only."DEFVAL{ trap }::={ snmpNotifyEntry 3}snmpNotifyStorageType OBJECT-TYPESYNTAXStorageTypeMAX-ACCESSread-create
STATUScurrentDESCRIPTION"The storage type for this conceptual row.
Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row."DEFVAL{ nonVolatile }::={ snmpNotifyEntry 4}snmpNotifyRowStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The status of this conceptual row.
To create a row in this table, a manager must
set this object to either createAndGo(4) or
createAndWait(5)."::={ snmpNotifyEntry 5}snmpNotifyFilterProfileTable OBJECT-TYPE
SYNTAXSEQUENCEOF SnmpNotifyFilterProfileEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table is used to associate a notification filter
profile with a particular set of target parameters."::={ snmpNotifyObjects 2}snmpNotifyFilterProfileEntry OBJECT-TYPESYNTAX SnmpNotifyFilterProfileEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry in this table indicates the name of the filter
profile to be used when generating notifications using
the corresponding entry in the snmpTargetParamsTable.
Entries in the snmpNotifyFilterProfileTable are created
and deleted using the snmpNotifyFilterProfileRowStatus
object."INDEX{IMPLIED snmpTargetParamsName }::={ snmpNotifyFilterProfileTable 1}
SnmpNotifyFilterProfileEntry ::=SEQUENCE{
snmpNotifyFilterProfileName SnmpAdminString,
snmpNotifyFilterProfileStorType StorageType,
snmpNotifyFilterProfileRowStatus RowStatus}snmpNotifyFilterProfileName OBJECT-TYPESYNTAXSnmpAdminString(SIZE(1..32))MAX-ACCESSread-create
STATUScurrentDESCRIPTION"The name of the filter profile to be used when generating
notifications using the corresponding entry in the
snmpTargetAddrTable."::={ snmpNotifyFilterProfileEntry 1}snmpNotifyFilterProfileStorType OBJECT-TYPESYNTAXStorageTypeMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The storage type for this conceptual row.
Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row."DEFVAL{ nonVolatile }::={ snmpNotifyFilterProfileEntry 2}
snmpNotifyFilterProfileRowStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The status of this conceptual row.
To create a row in this table, a manager must
set this object to either createAndGo(4) or
createAndWait(5).
Until instances of all corresponding columns are
appropriately configured, the value of the
corresponding instance of the
snmpNotifyFilterProfileRowStatus column is 'notReady'.
In particular, a newly created row cannot be made
active until the corresponding instance of
snmpNotifyFilterProfileName has been set."::={ snmpNotifyFilterProfileEntry 3}snmpNotifyFilterTable OBJECT-TYPESYNTAXSEQUENCEOF SnmpNotifyFilterEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The table of filter profiles. Filter profiles are used
to determine whether particular management targets should
receive particular notifications.
When a notification is generated, it must be compared
with the filters associated with each management target
which is configured to receive notifications, in order to
determine whether it may be sent to each such management
target.
A more complete discussion of notification filtering
can be found in section 6. of [SNMP-APPL]."::={ snmpNotifyObjects 3}snmpNotifyFilterEntry OBJECT-TYPESYNTAX SnmpNotifyFilterEntry
MAX-ACCESSnot-accessibleSTATUScurrent
DESCRIPTION"An element of a filter profile.
Entries in the snmpNotifyFilterTable are created and
deleted using the snmpNotifyFilterRowStatus object."INDEX{ snmpNotifyFilterProfileName,IMPLIED snmpNotifyFilterSubtree }::={ snmpNotifyFilterTable 1}
SnmpNotifyFilterEntry ::=SEQUENCE{
snmpNotifyFilterSubtree OBJECTIDENTIFIER,
snmpNotifyFilterMask OCTETSTRING,
snmpNotifyFilterType INTEGER,
snmpNotifyFilterStorageType StorageType,
snmpNotifyFilterRowStatus RowStatus
}snmpNotifyFilterSubtree OBJECT-TYPESYNTAXOBJECTIDENTIFIERMAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The MIB subtree which, when combined with the corresponding
instance of snmpNotifyFilterMask, defines a family of
subtrees which are included in or excluded from the
filter profile."::={ snmpNotifyFilterEntry 1}snmpNotifyFilterMask OBJECT-TYPESYNTAXOCTETSTRING(SIZE(0..16))MAX-ACCESSread-createSTATUScurrent
DESCRIPTION"The bit mask which, in combination with the corresponding
instance of snmpNotifyFilterSubtree, defines a family of
subtrees which are included in or excluded from the
filter profile.
Each bit of this bit mask corresponds to a
sub-identifier of snmpNotifyFilterSubtree, with the
most significant bit of the i-th octet of this octet
string value (extended if necessary, see below)
corresponding to the (8*i - 7)-th sub-identifier, and
the least significant bit of the i-th octet of this
octet string corresponding to the (8*i)-th
sub-identifier, where i is in the range 1 through 16.
Each bit of this bit mask specifies whether or not
the corresponding sub-identifiers must match when
determining if an OBJECT IDENTIFIER matches this
family of filter subtrees; a '1' indicates that an
exact match must occur; a '0' indicates 'wild card',
i.e., any sub-identifier value matches.
Thus, the OBJECT IDENTIFIER X of an object instance
is contained in a family of filter subtrees if, for
each sub-identifier of the value of
snmpNotifyFilterSubtree, either:
the i-th bit of snmpNotifyFilterMask is 0, or
the i-th sub-identifier of X is equal to the i-th
sub-identifier of the value of
snmpNotifyFilterSubtree.
If the value of this bit mask is M bits long and
there are more than M sub-identifiers in the
corresponding instance of snmpNotifyFilterSubtree,
then the bit mask is extended with 1's to be the
required length.
Note that when the value of this object is the
zero-length string, this extension rule results in
a mask of all-1's being used (i.e., no 'wild card'),
and the family of filter subtrees is the one
subtree uniquely identified by the corresponding
instance of snmpNotifyFilterSubtree."DEFVAL{ ''H }::={ snmpNotifyFilterEntry 2}snmpNotifyFilterType OBJECT-TYPE
SYNTAXINTEGER{included(1),excluded(2)}MAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object indicates whether the family of filter subtrees
defined by this entry are included in or excluded from a
filter. A more detailed discussion of the use of this
object can be found in section 6. of [SNMP-APPL]."DEFVAL{ included }::={ snmpNotifyFilterEntry 3}snmpNotifyFilterStorageType OBJECT-TYPESYNTAXStorageType
MAX-ACCESSread-createSTATUScurrentDESCRIPTION"The storage type for this conceptual row.
Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row."DEFVAL{ nonVolatile }::={ snmpNotifyFilterEntry 4}snmpNotifyFilterRowStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The status of this conceptual row.
To create a row in this table, a manager must
set this object to either createAndGo(4) or
createAndWait(5)."::={ snmpNotifyFilterEntry 5}
------ Conformance information----snmpNotifyCompliances OBJECTIDENTIFIER::={ snmpNotifyConformance 1}snmpNotifyGroups OBJECTIDENTIFIER::={ snmpNotifyConformance 2}------ Compliance statements----snmpNotifyBasicCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for minimal SNMP entities which
implement only SNMP Unconfirmed-Class notifications and
read-create operations on only the snmpTargetAddrTable."MODULE SNMP-TARGET-MIB
MANDATORY-GROUPS{ snmpTargetBasicGroup }OBJECT snmpTargetParamsMPModel
MIN-ACCESSread-onlyDESCRIPTION"Create/delete/modify access is not required."OBJECT snmpTargetParamsSecurityModel
MIN-ACCESSread-onlyDESCRIPTION"Create/delete/modify access is not required."OBJECT snmpTargetParamsSecurityName
MIN-ACCESSread-onlyDESCRIPTION"Create/delete/modify access is not required."
OBJECT snmpTargetParamsSecurityLevel
MIN-ACCESSread-onlyDESCRIPTION"Create/delete/modify access is not required."OBJECT snmpTargetParamsStorageType
SYNTAXINTEGER{
readOnly(5)}MIN-ACCESSread-onlyDESCRIPTION"Create/delete/modify access is not required.
Support of the values other(1), volatile(2),
nonVolatile(3), and permanent(4) is not required."OBJECT snmpTargetParamsRowStatus
SYNTAXINTEGER{
active(1)
}MIN-ACCESSread-onlyDESCRIPTION"Create/delete/modify access to the
snmpTargetParamsTable is not required.
Support of the values notInService(2), notReady(3),
createAndGo(4), createAndWait(5), and destroy(6) is
not required."MODULE-- This ModuleMANDATORY-GROUPS{ snmpNotifyGroup }OBJECT snmpNotifyTag
MIN-ACCESSread-onlyDESCRIPTION"Create/delete/modify access is not required."OBJECT snmpNotifyType
SYNTAXINTEGER{
trap(1)}MIN-ACCESSread-only
DESCRIPTION"Create/delete/modify access is not required.
Support of the value notify(2) is not required."OBJECT snmpNotifyStorageType
SYNTAXINTEGER{
readOnly(5)}MIN-ACCESSread-onlyDESCRIPTION"Create/delete/modify access is not required.
Support of the values other(1), volatile(2),
nonVolatile(3), and permanent(4) is not required."OBJECT snmpNotifyRowStatus
SYNTAXINTEGER{
active(1)}MIN-ACCESSread-only
DESCRIPTION"Create/delete/modify access to the
snmpNotifyTable is not required.
Support of the values notInService(2), notReady(3),
createAndGo(4), createAndWait(5), and destroy(6) is
not required."::={ snmpNotifyCompliances 1}snmpNotifyBasicFiltersCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for SNMP entities which implement
SNMP Unconfirmed-Class notifications with filtering, and
read-create operations on all related tables."MODULE SNMP-TARGET-MIB
MANDATORY-GROUPS{ snmpTargetBasicGroup }MODULE-- This ModuleMANDATORY-GROUPS{ snmpNotifyGroup,
snmpNotifyFilterGroup }::={ snmpNotifyCompliances 2}snmpNotifyFullCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for SNMP entities which either
implement only SNMP Confirmed-Class notifications, or both
SNMP Unconfirmed-Class and Confirmed-Class notifications,
plus filtering and read-create operations on all related
tables."MODULE SNMP-TARGET-MIB
MANDATORY-GROUPS{ snmpTargetBasicGroup,snmpTargetResponseGroup }MODULE-- This ModuleMANDATORY-GROUPS{ snmpNotifyGroup,
snmpNotifyFilterGroup }
::={ snmpNotifyCompliances 3}snmpNotifyGroup OBJECT-GROUPOBJECTS{
snmpNotifyTag,
snmpNotifyType,
snmpNotifyStorageType,
snmpNotifyRowStatus
}STATUScurrentDESCRIPTION"A collection of objects for selecting which management
targets are used for generating notifications, and the
type of notification to be generated for each selected
management target."::={ snmpNotifyGroups 1}snmpNotifyFilterGroup OBJECT-GROUPOBJECTS{
snmpNotifyFilterProfileName,
snmpNotifyFilterProfileStorType,
snmpNotifyFilterProfileRowStatus,
snmpNotifyFilterMask,
snmpNotifyFilterType,
snmpNotifyFilterStorageType,
snmpNotifyFilterRowStatus
}STATUScurrentDESCRIPTION"A collection of objects providing remote configuration
of notification filters."::={ snmpNotifyGroups 2}ENDSNMP-PROXY-MIB DEFINITIONS::=BEGINIMPORTSMODULE-IDENTITY,OBJECT-TYPE,snmpModules
FROM SNMPv2-SMI
RowStatus,StorageType
FROM SNMPv2-TC
SnmpEngineID,SnmpAdminStringFROM SNMP-FRAMEWORK-MIB
SnmpTagValueFROM SNMP-TARGET-MIB
MODULE-COMPLIANCE,OBJECT-GROUPFROM SNMPv2-CONF;snmpProxyMIB MODULE-IDENTITYLAST-UPDATED"200210140000Z"ORGANIZATION"IETF SNMPv3 Working Group"CONTACT-INFO"WG-email: snmpv3@lists.tislabs.com
Subscribe: majordomo@lists.tislabs.com
In message body: subscribe snmpv3
Co-Chair: Russ Mundy
Network Associates Laboratories
Postal: 15204 Omega Drive, Suite 300
Rockville, MD 20850-4601
USA
EMail: mundy@tislabs.com
Phone: +1 301-947-7107
Co-Chair: David Harrington
Enterasys Networks
Postal: 35 Industrial Way
P. O. Box 5004
Rochester, New Hampshire 03866-5005
USA
EMail: dbh@enterasys.com
Phone: +1 603-337-2614
Co-editor: David B. Levi
Nortel Networks
Postal: 3505 Kesterwood Drive
Knoxville, Tennessee 37918
EMail: dlevi@nortelnetworks.com
Phone: +1 865 686 0432
Co-editor: Paul Meyer
Secure Computing Corporation
Postal: 2675 Long Lake Road
Roseville, Minnesota 55113
EMail: paul_meyer@securecomputing.com
Phone: +1 651 628 1592
Co-editor: Bob Stewart
Retired"DESCRIPTION"This MIB module defines MIB objects which provide
mechanisms to remotely configure the parameters
used by a proxy forwarding application.
Copyright (C) The Internet Society (2002). This
version of this MIB module is part of RFC 3413;
see the RFC itself for full legal notices.
"REVISION"200210140000Z"-- 14 October 2002DESCRIPTION"Clarifications, published as
RFC 3413."REVISION"199808040000Z"-- 4 August 1998DESCRIPTION"Clarifications, published as
RFC 2573."REVISION"199707140000Z"-- 14 July 1997DESCRIPTION"The initial revision, published as RFC2273."::={ snmpModules 14}snmpProxyObjects OBJECTIDENTIFIER::={ snmpProxyMIB 1}
snmpProxyConformance OBJECTIDENTIFIER::={ snmpProxyMIB 3}------ The snmpProxyObjects group----snmpProxyTable OBJECT-TYPESYNTAXSEQUENCEOF SnmpProxyEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The table of translation parameters used by proxy forwarder
applications for forwarding SNMP messages."::={ snmpProxyObjects 2}snmpProxyEntry OBJECT-TYPESYNTAX SnmpProxyEntry
MAX-ACCESSnot-accessible
STATUScurrentDESCRIPTION"A set of translation parameters used by a proxy forwarder
application for forwarding SNMP messages.
Entries in the snmpProxyTable are created and deleted
using the snmpProxyRowStatus object."INDEX{IMPLIED snmpProxyName }::={ snmpProxyTable 1}
SnmpProxyEntry ::=SEQUENCE{
snmpProxyName SnmpAdminString,
snmpProxyType INTEGER,
snmpProxyContextEngineID SnmpEngineID,
snmpProxyContextName SnmpAdminString,
snmpProxyTargetParamsIn SnmpAdminString,
snmpProxySingleTargetOut SnmpAdminString,
snmpProxyMultipleTargetOut SnmpTagValue,
snmpProxyStorageType StorageType,
snmpProxyRowStatus RowStatus}snmpProxyName OBJECT-TYPESYNTAXSnmpAdminString(SIZE(1..32))MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The locally arbitrary, but unique identifier associated
with this snmpProxyEntry."::={ snmpProxyEntry 1}snmpProxyType OBJECT-TYPE
SYNTAXINTEGER{read(1),write(2),trap(3),inform(4)}MAX-ACCESSread-createSTATUScurrentDESCRIPTION"The type of message that may be forwarded using
the translation parameters defined by this entry."::={ snmpProxyEntry 2}snmpProxyContextEngineID OBJECT-TYPESYNTAXSnmpEngineID
MAX-ACCESSread-createSTATUScurrentDESCRIPTION"The contextEngineID contained in messages that
may be forwarded using the translation parameters
defined by this entry."::={ snmpProxyEntry 3}snmpProxyContextName OBJECT-TYPESYNTAXSnmpAdminStringMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The contextName contained in messages that may be
forwarded using the translation parameters defined
by this entry.
This object is optional, and if not supported, the
contextName contained in a message is ignored when
selecting an entry in the snmpProxyTable."::={ snmpProxyEntry 4}
snmpProxyTargetParamsIn OBJECT-TYPESYNTAXSnmpAdminStringMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object selects an entry in the snmpTargetParamsTable.
The selected entry is used to determine which row of the
snmpProxyTable to use for forwarding received messages."::={ snmpProxyEntry 5}snmpProxySingleTargetOut OBJECT-TYPESYNTAXSnmpAdminStringMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object selects a management target defined in the
snmpTargetAddrTable (in the SNMP-TARGET-MIB). The
selected target is defined by an entry in the
snmpTargetAddrTable whose index value (snmpTargetAddrName)
is equal to this object.
This object is only used when selection of a single
target is required (i.e. when forwarding an incoming
read or write request)."::={ snmpProxyEntry 6}snmpProxyMultipleTargetOut OBJECT-TYPESYNTAXSnmpTagValueMAX-ACCESSread-createSTATUScurrentDESCRIPTION"This object selects a set of management targets defined
in the snmpTargetAddrTable (in the SNMP-TARGET-MIB).
This object is only used when selection of multiple
targets is required (i.e. when forwarding an incoming
notification)."::={ snmpProxyEntry 7}
snmpProxyStorageType OBJECT-TYPESYNTAXStorageTypeMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The storage type of this conceptual row.
Conceptual rows having the value 'permanent' need not
allow write-access to any columnar objects in the row."DEFVAL{ nonVolatile }::={ snmpProxyEntry 8}snmpProxyRowStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrentDESCRIPTION"The status of this conceptual row.
To create a row in this table, a manager must
set this object to either createAndGo(4) or
createAndWait(5).
The following objects may not be modified while the
value of this object is active(1):
- snmpProxyType
- snmpProxyContextEngineID
- snmpProxyContextName
- snmpProxyTargetParamsIn
- snmpProxySingleTargetOut
- snmpProxyMultipleTargetOut"::={ snmpProxyEntry 9}------ Conformance information----snmpProxyCompliances OBJECTIDENTIFIER::={ snmpProxyConformance 1}snmpProxyGroups OBJECTIDENTIFIER::={ snmpProxyConformance 2}
------ Compliance statements----snmpProxyCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for SNMP entities which include
a proxy forwarding application."MODULE SNMP-TARGET-MIB
MANDATORY-GROUPS{ snmpTargetBasicGroup,snmpTargetResponseGroup }MODULE-- This ModuleMANDATORY-GROUPS{ snmpProxyGroup }::={ snmpProxyCompliances 1}snmpProxyGroup OBJECT-GROUP
OBJECTS{
snmpProxyType,
snmpProxyContextEngineID,
snmpProxyContextName,
snmpProxyTargetParamsIn,
snmpProxySingleTargetOut,
snmpProxyMultipleTargetOut,
snmpProxyStorageType,
snmpProxyRowStatus
}STATUScurrentDESCRIPTION"A collection of objects providing remote configuration of
management target translation parameters for use by
proxy forwarder applications."::={ snmpProxyGroups 3}END